Digital file distribution in a social network system

ABSTRACT

Systems and methods for obtaining a digital file similar to one used by a device associated with a member of a social network are provided. Digital file information about the digital file is stored on a web-based social network database. The digital file may be located on the same server as the web-based social network database or a third party server such as a mobile phone carrier. A user of the web-based social network database requesting the digital file may require a different format of the digital file than that used by the device of the member. If a different format is requested by the user, a server finds or converts the digital file to be compatible for use by a device specified by the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/475,673, filed on May 18, 2012, which is a continuation of U.S.patent application Ser. No. 11/701,698, filed on Feb. 2, 2007, which areincorporated by reference herein in their entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to digital contact files, andmore particularly to systems and methods for digital file distributionin a social network.

2. Description of Related Art

Conventionally, members of a social network who desire a similar digitalfile, such as a ringtone, game, image file or any other file used by adevice, as another member of the social network have limited methods toobtain the digital file. One method is for the owner of the digital fileto make a copy and transfer it to the member who desires the copy. Insome situations, however, the owner is not available to make the copy,does not have permission to make a copy or does not have a device thatcan make a copy. In these situations, the member who desires a copy maybe required to seek the digital file from a third party. In somesituations, this requires the member to search the Internet for thedigital file or to request the digital file from a publisher of thedigital file.

For some members who desire the digital file, a version of the digitalfile may not be available for their device. For example, if a ringtonehas only been modified for use on a Verizon mobile phone, a member witha Nokia mobile phone may not be able to use that version of the digitalfile if the Verizon mobile phone and Nokia mobile phone have differentringtone formats. In this situation, the member with the Nokia mobilephone may need to request the ringtone from a Nokia wireless carrier.

Other members who desire a digital photo taken with a friend's cameramay be able to have the friend send the digital photo, but may be unableto edit the digital photo so as to have the digital photo displayproportionally on their device. What is needed are improved methods andsystems for automatically locating or converting digital filescompatible for use by devices.

SUMMARY OF THE INVENTION

Systems and methods are provided for distributing a digital file betweenusers of a peer-to-peer network using a web-based social networkdatabase. An exemplary method according to one embodiment of theinvention includes storing identification information of the digitalfile in a record of a first user of a web-based social network database,receiving a request from a second user of the web-based social networkdatabase for the digital file, locating a source of a similar digitalfile, and facilitating the transfer of the similar digital file from thesource to the device.

An exemplary system according to one embodiment of the present inventionincludes a web-based social network database and a finder module. Theweb-based social network database stores identification information ofthe digital file in a record of a first user of the web-based socialnetwork database and receives a request from a second user for thedigital file wherein the request is partially based on theidentification information in the record of the first user. A findermodule locates a source of a similar digital file and facilitates thetransfer of the similar digital file from the source to a device.

The digital file may be a ringtone, game, image file or any other fileused by a device. The digital file may be located on a server which alsocontains the web-based social network database or a different server,such as a third party server. The server may recommend additionaldigital files. The server may automatically detect the device being usedto request the digital file or the user may provide information aboutthe device. The server may locate the source of the digital file usingthe device information to ensure that the digital file is compatiblewith the device. The server may convert the digital file to a format tobe used by the device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary architecture for distribution of adigital file;

FIG. 2 illustrates an exemplary architecture for requesting a digitalfile;

FIG. 3 is an exemplary screenshot of user contact and generalinformation from a record of a web-based social network database;

FIG. 4 is an exemplary screenshot of digital file information from arecord of a web-based social network database;

FIG. 5 is an exemplary screenshot of a listing of available digitalfiles;

FIG. 6 is a flow chart for an exemplary method for requesting digitalfile information; and

FIG. 7 is a flow chart for an exemplary method for requesting a digitalfile.

DETAILED DESCRIPTION OF THE INVENTION

Systems and methods for distributing to a user's device a digital filelisted in a record of another user of a web-based social networkdatabase are disclosed. The web-based social network database is anydatabase that may be accessed over a network and may store peer-to-peernetwork information about a user in one or more records. Peer-to-peernetwork information may include information about people, relationships,contacts, social activities, groups, events, user devices andinformation about digital files on user devices.

The distribution of the digital file is requested by the user afterobtaining information that another user has the digital file. The usermay obtain the information about the digital file from the other user inperson, for example, by hearing his ringtone, or by viewing the otheruser's record of the web-based social network database.

In various embodiments, the device is a computer or a mobile device,such as a mobile phone, a cell-phone, a smart-phone, a personal digitalassistant (PDA), a notebook computer, a laptop computer or a hand-heldgame console. The digital file is any type of file that can be accessedby a computer or a mobile device, such as a ringtone, a game, a picture,an image, a movie, a video, an audiovisual, a pictorial or any otherdigital document, such as a resume, a calendar, a presentation, aslideshow, an album or an e-mail. The digital file may be in any formatthat can be read by a computer or mobile device, such as those savedusing Microsoft (MS) Word, MS Excel, MS PowerPoint, MS Access or anyformat that can be read by a mobile device such as files formatted inJPEG, MPEG, PDF, Multimedia Messaging Service (MMS), Short MessagingService (SMS) or WAP Push.

The digital file can also be a social map and/or a social timeline. Asocial map in one embodiment is a display of the interactions,relationships and experiences of individuals or groups of individualscomprising the web-based social network database, as described in U.S.Provisional Patent Application Ser. No. 60/750,844 filed on Dec. 14,2005 for “Systems and Methods for Social Mapping,” and incorporatedherein by reference. A social timeline in one embodiment is achronological listing of a user selected subset of individuals of theweb-based social network database in social categories, as described inU.S. Provisional Patent Application Ser. No. 60/753,810 filed on Dec.23, 2005 for “Systems and Methods for Social Timeline,” and incorporatedherein by reference.

FIG. 1 illustrates an exemplary architecture 100 for distribution of adigital file. Architecture 100 comprises devices 110 and 120, a network130, a server 140, and publishers 150 and 160. Server 140 comprises aweb-based social network database 170. Devices 110 and 120 may beoperated by a same user or by different users.

The network 130 provides the medium for communication between two ormore components, such as between server 140 and device 110. Network 130may include an Internet network and/or wireless or wired networks suchas mobile device carrier networks or any other network that can be usedfor communication between a server and a client.

The server 140 allows a user of device 120 to obtain a similar digitalfile as on device 110 where information about the digital file is storedon the web-based social network database 170. The web-based socialnetwork database 170 stores information about a user and/or the user'sdevice 110 in a record. For example, a user's record contains title andartist information about ringtones on the user's device 110. Theringtone information may include the title, musician, publisher,copyright, and any other information associated with a ringtone, such asformat type, duration of ringtone, and device compatibility information.

The web-based social network database 170 is designed to storedinformation that may have been entered manually by the user or may havebeen obtained automatically by server 140 when device 110 is being usedto communicate with the web-based social network database 170.

In some embodiments, a record contains information about severalringtones per device and an associated use for each ringtone, e.g., ifthe caller is known, unknown or is using caller ID blocking. In otherembodiments, the record stores information on contacts stored in device110 and any associated assigned ringtones, for example, the contact‘mom’ may be associated with the ringtone based on Mozart, “Symphony29,” when she is calling from her home and Mozart, “Symphony 31,” whenshe is calling from her mobile phone. In various embodiments, the device110 ringtone information is automatically updated after any changes aremade.

In some embodiments, a user of device 120 may learn of a digital file ondevice 110 and desire to have a similar digital file loaded onto device120. The user of device 120 may ask the user of device 110 foridentification information about the digital file or may view a recordof the web-based social network database 170 to find information aboutthe digital file. In various embodiments, the user of device 120 mayrequest the digital file from server 140. Server 140 may have a versionof the digital file compatible with device 120 or may know a source of acompatible digital file for use by device 120, such as publisher 160.

In various embodiments, after server 140 locates the digital file fordevice 120, server 140 facilitates the transfer of the digital file to amemory assessable by device 120. In some embodiments, server 140 mayload the digital file directly onto device 120. In other embodiments,server 140 may have a publisher load the digital file onto device 120 orsome other memory location assessable by device 120.

FIG. 2 illustrates an exemplary architecture 200 for requesting adigital file. In various embodiments, architecture 200 includes device120, network 130 and server 140. Device 120 may include device display210, a device contact application 220 and memory 230. The device contactapplication 220 may contain a contact content request module (not shown)used for requesting contact information and a contact file (not shown)used for storing contact information. Server 140 contains a servercontact application 240, a device specification module 250, a findermodule 260, a recommendation module 270, an accounts module 280, acontact privacy settings module 285, a conversion module 290 and amemory 295. In various embodiments, server 140 may exclude some of thesemodules and/or add other modules, e.g., server 140 may contain theweb-based social network database 170, finder module 260 and memory 295.

In various embodiments, server 140 uses server contact application 240to communicate with device 120. After device 120 establishescommunication with server 140 for the first time, device contactapplication 220 may be downloaded onto device 120 for use withidentification and/or further communication. Device contact application220 may format information from the web-based social network database170 for device display 210. Device contact application 220 may alsocontain the contact information about other users with records on theweb-based social network database 170. In various embodiments, device120 uses memory 230 to store device contact application 220 and/or anyinformation downloaded from the web-based social network database 170.

In some embodiments, server 140 uses device specification module 250 todetermine specifications of device 120 used by the user requesting thedigital file. Device specification module 250 may contain specificationsfor a wide variety of devices. After device specification module 250recognizes the type of device 120 being used to communicate with server140, device specification module 250 formats information to accommodatethe specification particular for device 120. For example, devicespecification module 250 automatically recognizes that a user is using aBlackBerry device to communicate with server 140 and formats informationto display on device display 210 of the BlackBerry device.

In various embodiments, server 140 includes finder module 260. After auser makes a request for a digital file, finder module 260 searches fora digital file similar to the requested digital file. As differentdevices may require different formats for different types of files, insome embodiments, finder module 260 determines an appropriate digitalfile that can be used by device 120 before searching for a digital file.Finder module 260 may obtain information about device 120 from thedevice specification module 250 and/or the web-based social networkdatabase 170. In various embodiments, finder module 260 searches for thedigital file until the digital file is found in the web-based socialnetwork database 170 and/or third party publishers, such as publisher150 and publisher 160, respectively.

In some embodiments, server 140 includes recommendation module 270.After a user makes a request for a digital file, recommendation module270 searches for digital files related to the requested digital file inwhich the user might also have an interest. Recommendation module 270may use information about characteristics of the user and/or informationabout the requested digital file as recommendation criteria.Characteristics of the user may include, but are not limited to, age,song preferences, education, prior purchases, surveys, information inthe user's record or any other information that may be useful todetermine recommendations. Information about the requested digital filemay include the title, genre, related songs, related artists or anyother information that may be useful to determine recommendations.

In various embodiments, recommendation module 270 runs on the web-basedsocial network database 170 or a different database (not shown).Recommendation module 270 provides the user with a broader selection ofdigital files. Also, if the requested digital file is not available in ausable format for device 120, recommendation module 270 at leastprovides the user with a selection of alternative digital files.

Server 140 may include an accounts module 280 to account for the digitalfile location, source, price and any other information necessary toaccount and keep track of the transfer of digital files in an accountingand billing system. For example, if a user downloads a ringtone from apublisher, then accounts module 280 collects price, purchase time,delivery time and method of payment. Accounts module 280 may alsoaccount for quantity discount information, spending limits or any otherinformation that may be used to account for a transaction between theuser and publisher. In alternative embodiments, accounts module 280 is apassive system, only keeping track of how much the user pays a publisherdirectly, thereby knowing how much commission, if any, may be due.

In various embodiments, the accounts module 280 may work with digitalrights management (DRM) technologies. DRM is any of several technologiesused by a publisher to restrict usage of and/or access to digital files.Some DRM technologies may include such items as product activationrequirements, digital watermarking, Content Scrambling System (CSS) orother scrambling methods. Account module 280 may coordinate with one ormore of the device specification module 250, finder module 260 andconversion module 290 to address any requirements of a DRM technologywhile providing the digital file to a user. For example, a user may berequired to accept a copyright or other agreement prior to obtaining thedigital file.

In various embodiments, the server 140 may ensure the integrity of theDRM technology. For example, the conversion module 290 may re-encrypt akey when converting from one medium to another.

In some embodiments, server 140 may include the contact privacy settingsmodule 285. The contact privacy settings module 285 stores contactprivacy settings for contacts in the web-based social network database170. The contact privacy settings module 285 allows a user to permitand/or restrict other users' view of information stored in the user'srecord. For example, a user may designate other users as ‘friends’ toview all the records of the user and may designate some users as‘co-workers’ to have a limited access to a few records. Accordingly, auser may view records of the web-based social network database 170 ofother users for which the user has permission to view.

Server 140 may include conversion module 290 to modify a digital file toenable use by device 120. The conversion module 290 may perform displayformatting operations similar to those in device specification module250 or perform formatting operations, such as removing a file header andreplacing it with a file header compatible with device 120. For example,the conversion module 290 may change a ringtone used by a Nokia mobilephone to be compatible for use by an LG mobile phone. In anotherexample, the conversion module 290 may change a file from a Tagged ImageFile Format (TIFF) to a JPEG File Interchange Format (JFIF).

In various embodiments, server 140 includes memory 295 to store and runapplications and/or modules. Memory 295 may also contain the records ofthe web-based social network database 170 and may serve as a repositoryfor digital files. In other embodiments, applications and modules mayreside in memory on several servers (not shown).

It will readily be appreciated by one of ordinary skill in the art thatthe web-based social network database 170 may also function as astandalone application, separate from server 140. Multiple combinationsand locations can be configured for the applications and modulesdiscussed herein. For example, each module may reside on a differentserver. All of these variations remain within the scope of claimedembodiments.

FIG. 3 is an exemplary screenshot of user contact and generalinformation from a record 300 of the web-based social network database170. The screenshot illustrates some information shown to a user of theweb-based social network database 170. In various embodiments, usercontact and general information in the screenshot of the record 300includes a name field 310, a portrait 320, a link to a recording 330, anassociated file listing 340, links to music files 350, music fileselections 360 and a navigation link 370. In various embodiments, theuser using device 120 may search and/or select information in the recordof another user. The information needed to generate the screenshot ofthe record 300 may reside in memory 230 of device 120 or in some otherlocation, such as memory 295 of server 140.

The name field 310 identifies an owner of the record. The portrait 320may also help identify the owner. The link to a recording 330 may linkto a simple message. Other information may be displayed in one screen ondevice 120 depending on the device display 210, such as workinformation, personal information and hobbies.

The associated file listing 340 provides a listing of available digitalfile information, such as links to music files 350. Music fileselections 360 may be selected to display additional information aboutthe selected digital file. Music file selections 360 may includeinformation about ringtones, MP3s or any other music digital file. Insome embodiments, navigation link 370 may be provided to help navigatethrough information in records of the web-based social network database170.

In various embodiments, the amount of information displayed on devicedisplay 210 may vary due to such factors as the size of device display210 and/or any settings of device specification module 250 to format thedisplayed information. Other factors that determine the amount ofinformation to present on device display 210 may include settings indevice contact application 220 and/or server contact application 240.

FIG. 4 is an exemplary screenshot of digital file information from arecord 400 of a web-based social network database 170. In variousembodiments, the screenshot of information from record 400 includesrecord identification information 410 and a digital file link 420. Therecord identification information 410 helps to identify that the userhas navigated to a desired record. Digital file link 420 may be selectedif a user would like a copy of the digital file. The selection ofdigital file link 420 may be performed in various ways and may be devicespecific. For example, if device 120 is an LG VX8100, then the user maynavigate using navigation keys and press an ‘OK’ button (not depicted)on the device 120 when the user wishes to select digital file link 420.In various embodiments, the display is arranged to permit usefulnavigation and/or sized for the device display 210.

FIG. 5 is an exemplary screenshot of a listing of available digitalfiles 500. In some embodiments, the listing of available digital files500 contains a record title 510, digital file information 520, arecommendation listing 530, pricing information 540, and quantitydiscount pricing 550. The record title 510 may be specific for a type ofdigital file a user is requesting, e.g., record title 510 is ‘Ringtones’when the user selects to download a ringtone.

Digital file information 520 contains the artist, title and otherinformation about the digital file. The user may view the digital fileinformation 520 after selecting digital file link 420. In variousembodiments, digital title information 520 contains information thatfinder module 260 has determined to be the closest match to the userrequested digital file. In some embodiments, if finder module 260 cannotlocate a title similar to the requested digital file, finder module 260may either request the conversion module 290 to generate a compatibledigital file or return a message to device 120 indicating that therequested digital file is not available at this time. In otherembodiments, if finder module 260 finds multiple digital files similarto the requested digital file, then the title of the requested digitalfile 520 may list information about the similar digital files.

The recommendation listing 530 lists the titles and respective artistsof digital files that recommendation module 270 may determine to be ofinterest to the user. These digital files are selected to be compatiblewith device 120. In various embodiments, if recommendation module 270cannot find a predetermined number of usable digital files, e.g., threedigital files, then recommendation module 270 may request the conversionmodule 290 to generate more digital files compatible with device 120.

Optionally, pricing information 540 and any quantity discount pricing550 is displayed for respective digital files. In some embodiments, if auser desires the digital file at the listed price, the user may selectthe pricing information 540 to download the digital file. In otherembodiments, the pricing information 540 may be a list and the user mayselect a title to download the digital file. In various embodiments, theuser may select multiple digital files prior to downloading.

FIG. 6 is a flow chart 600 for an exemplary method for requestingdigital file information, according to one embodiment of the presentinvention. In step 610, the web-based social network database 170receives a request from a user of the web-based social network database170 for information about a digital file contained in a record ofanother user. When requesting digital file information 520, it is notnecessary for the user to know specific information about the identityof the digital file. For example, if a user hears the ringtone and doesnot recognize the artist, the user can still request that ringtone fromthe record. Knowledge about the existence of the digital file may beobtained by viewing another user's device or by viewing another user'srecord.

In step 620, the web-based social network database 170 communicates witha privacy module (not shown) located on server 140 to determine if theuser requesting digital file information 520 has permission to view therequested information.

In step 630, the web-based social network database 170 and devicespecification module 250 determine if the user requesting the digitalfile information 520 has a device capable of using the type of file thatthe user is requesting. For example, if device 120 does not storeringtones and a user of device 120 requests digital file information 520about a ringtone, the web-based social network database 170 may relaythis incompatibility to the user.

In step 640, the web-based social network database 170 prepares theresponse with the digital file information 520. In various embodiments,the web-based social network database 170 contains the digital fileinformation 520. In some embodiments, the web-based social networkdatabase 170 searches third party databases for digital file information520.

In step 650, the web-based social network database 170 communicates witha device user settings module (not shown) to determine if any usersettings have been specified. For example, if the user of device 120 hasspecified information to be presented on the top half of device display210, then the digital file information 520 may be formatted to fit inthe top half of device display 210.

In step 660, the web-based social network database 170 sends the digitalfile information 520 to device 120. In some embodiments, the web-basedsocial network database 170 may send additional information about thefile, such as the record identification information 410 and the namefield 310. In various embodiments, the web-based social network database170 may send other digital file listings associated with the record fromwhich the digital file information 520 was requested.

FIG. 7 is a flow chart 700 for an exemplary method for requesting adigital file, according to one embodiment of the present invention.After the user receives digital file information 520, which may berequested as shown in flow chart 600, the user may request to downloadthe digital file.

In step 710, the web-based social network database 170 receives arequest from the user to download a digital file. In variousembodiments, the web-based social network database 170 determines if therequested digital file is available in a usable format for device 120.The user requesting the digital file may provide information aboutdevice 120 to the web-based social network database 170. In otherembodiments, the server contact application 240 may determine the devicetype and/or may reference third party information as to capabilities ofdevice 120.

In step 720, optionally, the web-based social network database 170queries device specification module 250 to determine types of digitalfiles that are compatible with device 120. In some embodiments, theweb-based social network database 170 may query device specificationmodule 250 after some digital files are located to determine if they arecompatible with device 120.

In step 730, the web-based social network database 170 queries findermodule 260 to locate a digital file similar to the requested digitalfile. In some embodiments, finder module 260 uses the information fromthe device specification module 250 in step 720 to find a compatibledigital file for device 120. In other embodiments, finder module 260finds and retrieves any similar digital file and converts the digitalfile using the conversion module 290 so the digital file will becompatible with device 120.

In step 740, the web-based social network database 170 queriesrecommendation module 270 to provide the recommendation listing 530. Insome embodiments, the web-based social network database 170 may usefinder module 260 to locate recommended digital files.

In step 750, the web-based social network database 170 receives digitalfile pricing information associated with the requested digital file. Invarious embodiments, the information is provided by finder module 260and/or third party servers. In some embodiments, the pricing informationis located and/or generated in a pricing module (not shown) on server140.

In step 760, the web-based social network database 170 receives therecommendation listing 530 and associated pricing information. Invarious embodiments, the information is provided by finder module 260and/or a third party server.

In step 770, the web-based social network database 170 sends digitalfile information 520 and associated pricing information to device 120and, optionally, the recommendation listing 530 and associated pricinginformation.

In step 780, the user selects a digital file to download, if desired. Ifthe user decides not to select a digital file, the process ends. If theuser requests the digital file the process continues to step 790.

In step 790, the web-based social network database 170 facilitates thetransmission of the digital file to device 120, to a memory accessibleby device 120 or to a third party device. In various embodiments, theuser will have the option of where and how the source is to deliver thedigital file, e.g., the user may send a ringtone to a friend as abirthday present. In some embodiments, the web-based social networkdatabase 170 may allow the user to send a text message informing a thirdparty recipient of a pending digital file download. In variousembodiments, the web-based social network database 170 requests a thirdparty to transmit the digital file. In some embodiments, the digitalfile is sent to a server to be downloaded by device 120 at a later time.

In step 795, the web-based social network database 170 communicates withaccounts module 280 regarding any transactions and/or relatedinformation. Accounts module 280 may contain information pertaining toaccounting, billing, addresses, digital files requested, digital filesdownloaded or any other information necessary to properly account forInternet transactions, such as state tax information.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. For example, any of the elements associated with requestingand obtaining a digital file from a web-based social database may employany of the desired functionality set forth hereinabove. The methodsshown in FIGS. 6 and 7 are exemplary and some steps may be omitted oradded and still fall within the present invention. Thus, the breadth andscope of a preferred embodiment should not be limited by any of theabove-described exemplary embodiments.

What is claimed is:
 1. A computer-implemented method comprising: storingidentification information of a digital file associated with a firstuser of a social networking system; receiving a request from a seconduser of the social networking system for the digital file, the seconduser connected to the first user by a social networking relationshipwithin the social networking system, the social networking relationshiprepresented by a social map comprising interactions and sharedexperiences between the second user and the first user; responsive toreceiving the request from the second user, determining an actionrequired of the second user under a digital rights management (DRM)scheme of a third-party source of the digital file, the third-partysource external to the social networking system, the action required forthe second user to access the digital file; causing the second user totake the required action responsive to determining the required action;and causing the digital file to be transferred from the third-partysource of the digital file to a device of the second user responsive tothe second user taking the required action.
 2. The method of claim 1,wherein the required action comprises accepting a copyright agreementassociated with the digital file.
 3. The method of claim 1, furthercomprising re-encrypting a key associated with the DRM scheme.
 4. Themethod of claim 1, wherein the DRM scheme is associated with apublisher.
 5. The method of claim 1, wherein the digital file isselected from the group consisting of a ringtone, a game, and an imagefile.
 6. The method of claim 1, wherein the source of the digital fileis a device of the first user.
 7. The method of claim 1, furthercomprising receiving device information from the device associated withthe second user, the device information representing specifications ofthe device; storing the device information; and locating a version ofthe digital file compatible with the device based on the deviceinformation.
 8. A non-transitory computer-readable storage mediumstoring instructions for providing a social networking system, theinstructions executed by a processor and causing the processor to: storeidentification information of a digital file associated with a firstuser of a social networking system; receive a request from a second userof the social networking system for the digital file, the second userconnected to the first user by a social networking relationship withinthe social networking system, the social networking relationshiprepresented by a social map comprising interactions and sharedexperiences between the second user and the first user; responsive toreceiving the request from the second user, determine an action requiredof the second user under a digital rights management (DRM) scheme of athird-party source of the digital file, the third-party source externalto the social networking system, the action required for the second userto access the digital file; cause the second user to take the requiredaction responsive to determining the required action; and cause thefirst digital file to be transferred from the third-party source of thedigital file to a device of the second user responsive to the seconduser taking the required action.
 9. The computer-readable storage mediumof claim 8, wherein the required action comprises accepting a copyrightagreement associated with the digital file.
 10. The computer-readablestorage medium of claim 8, the instructions further causing theprocessor to re-encrypt a key associated with the DRM scheme.
 11. Thecomputer-readable storage medium of claim 8, wherein the DRM scheme isassociated with a publisher.
 12. The computer-readable storage medium ofclaim 8, wherein the digital file is selected from the group consistingof a ringtone, a game, and an image file.
 13. The computer-readablestorage medium of claim 8, wherein the source of the digital file is adevice of the first user.
 14. The computer-readable storage medium ofclaim 8, the instructions further causing the processor to: receivedevice information from the device associated with the second user, thedevice information representing specifications of the device; store thedevice information; and locate a version of the digital file compatiblewith the device based on the device information.
 15. A computer systemcomprising: a processor; and a memory storing instructions executable bythe processor to: store identification information of a digital fileassociated with a first user of a social networking system; receive arequest from a second user of the social networking system for thedigital file, the second user connected to the first user by a socialnetworking relationship within the social networking system, the socialnetworking relationship represented by a social map comprisinginteractions and shared experiences between the second user and thefirst user; responsive to receiving the request from the second user,determine an action required of the second user under a digital rightsmanagement (DRM) scheme of a third-party source of the digital file, thethird-party source external to the social networking system, the actionrequired for the second user to access the digital file; cause thesecond user to take the required action responsive to determining therequired action; and cause the first digital file to be transferred fromthe third-party source of the digital file to a device of the seconduser responsive to the second user taking the required action.
 16. Thecomputer system of claim 15, wherein the required action comprisesaccepting a copyright agreement associated with the digital file. 17.The computer system of claim 15, the memory further storing instructionsto cause the processor to re-encrypt a key associated with the DRMscheme.
 18. The computer system of claim 15, wherein the DRM scheme isassociated with a publisher.